docs: establish Codex alignment roadmap - #180
Merged
Merged
Conversation
This was referenced Aug 1, 2026
This was referenced Aug 1, 2026
oratis
marked this pull request as ready for review
August 2, 2026 06:34
Owner
Author
Review: approved ✅Scope: docs + CI only — no runtime behavior change, which matches the stated intent. What I verified
Note (not blocking): marking Validation: CI green on both runners. Locally at the stack tip (#210): typecheck, lint ( |
This was referenced Aug 2, 2026
oratis
added a commit
that referenced
this pull request
Aug 2, 2026
…ajors (#215) Covers the 31-PR Codex alignment stack (#180-#210) plus the dependency work (#211-#214, #155, #177-#179). Leads with the security section because that is what this release is: the central tool gate could be skipped entirely when `mode` was omitted (#181), and the desktop renderer held provider credentials (#192). Upgrade notes call out the two things a user could otherwise be surprised by — the ~6.7 MB → ~115 MB desktop size increase from the Node sidecar, and that the plugin capability RPC is not an OS boundary. Co-authored-by: t <t@t> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
DeepCode's clients share
runAgentbut assemble sessions, permissions, hooks, sandboxing, cancellation, and credentials differently. The review also found that VS Code/LSP can omit the central permission gate, LSP abort does not cancel work, the desktop renderer holds provider credentials, and a TypeScript server cannot simply be moved into the current Tauri bundle without a packaging decision.This PR makes those facts explicit, defines the decision order, and creates a trustworthy baseline before runtime changes begin.
Impact
No runtime behavior changes. Contributors get one current plan, a root
AGENTS.md, accurate setup/test commands, and CI coverage for previously omitted TypeScript projects and the Rust backend.Validation
pnpm docs:checkpnpm typecheckpnpm lint(3 pre-existing warnings, no errors)pnpm format:checkpnpm test(910 passed, 12 conditional skips)pnpm buildcargo check --manifest-path apps/desktop/src-tauri/Cargo.toml --lockedcargo test --manifest-path apps/desktop/src-tauri/Cargo.toml --locked(28 passed)